Conversation
|
Towards: CON-308 |
| <uri> is formatted as **kmstype:[key=value;...]?[key=value&...]**. The **;**-separated | ||
| parameters identify the KMS, and **&**-separated parameters contain credentials. | ||
|
|
||
| : Supported KMS types: |
There was a problem hiding this comment.
Do we want capi, mackms, softkms and sshagentkms here too, to make the list from https://github.com/smallstep/step-kms-plugin/blob/main/main.go#L19-L29 complete? They're not all as well-known as the ones you already listed, but capi can be useful.
There was a problem hiding this comment.
I'm okay with just having the most common options shown, and if people dig into step-kms-plugin for the others. I guess I'm sensitive to the length of the help text.
Co-authored-by: Herman Slatman <hslatman@users.noreply.github.com>
Co-authored-by: Herman Slatman <hslatman@users.noreply.github.com>
|
Btw, I changed the title and moved the issue number for tracking to a comment. Generally it's sufficient to put it in the git commit message, and it will be tracked. At least for the internal projects. No need to litter the title with non-functional metadata. |
No description provided.